Case study: Morrisville Craftsman Remodeling — Josefina Terrera Studio
Josefina Terrera STUDIO

CASE STUDY — 03 / 05

Morrisville Craftsman — a field manual, not a brochure.

A remodeling contractor in Morrisville, NC. Homeowners don't trust contractor brochures — they trust specifics. So the whole site is built like a spec sheet: warm paper, ink, amber, monospace data, and interactive modules that give real answers before the first call.

CONTRACTOR MORRISVILLE, NC 2026 10 PAGES · 0 DEPENDENCIES

THREE DECISIONS — WRITTEN FOR OWNERS, VERIFIABLE BY DEVELOPERS

01

An honest scope estimator

Three questions, one realistic price bracket — the matrix lives in plain JavaScript on the page. It filters tire-kickers, and the honesty of showing a bracket at all earns more trust than any testimonial.

02

Local operating intelligence

A tabbed module answers the constraints locals actually have — HOA rules, townhome access, working from home during construction, driveway protection, prepping to sell, rentals. Content that proves the crew has been on these exact streets.

03

Zero dependencies, one script

Before/after sliders, count-up numbers, the sticky estimate panel, a process timeline — all hand-written, no libraries. One script serves all ten pages, with every module guarding its own DOM so nothing ever errors.

10

PAGES — SERVICES, CASES, ABOUT

6

INTERACTIVE MODULES, HAND-WRITTEN

0

LIBRARIES OR FRAMEWORKS

'26

LAUNCHED — RESULTS BEING MEASURED

The client's problem

Remodeling is a trust purchase with a five-figure price tag, and every contractor site says the same three adjectives. The way out was specificity: real process steps, real constraint knowledge, real price brackets — presented like documentation, because documentation is what careful people trust.

The estimate form ships with a demo mode and a single endpoint constant, so the owner could go live with any form service in one line.

What a developer would notice

Content and behavior are separated on purpose: scenario copy, process steps, and the pricing matrix are plain data structures at the top of the script, editable without touching a line of logic. The slider, tabs, and count-ups are each a self-contained module that checks for its own markup before running.

Ten pages, two stylesheets, one script — a system a future maintainer can hold in their head in an afternoon.

CLIENT SYSTEM #F4F1EA #C0782B #2C4A63 #1A1A17 Space Grotesk · Inter · IBM Plex Mono

CLIENT NOTE — PLACEHOLDER, SWAP IN THE REAL QUOTE

“One or two sentences in the client's own words — clearer inquiries, an easier process, or the site paying for itself.”

CLIENT NAME · BUSINESS

← PREV: CARY CLEARVIEW NEXT CASE Restaurant — in progress →